System and method of providing a geographic view of nodes in a wireless network

ABSTRACT

A geographic view rendering tool receives geographic location data for nodes in a wireless network and renders a geographic view displaying the nodes at their corresponding geographic locations. The geographic view may be displayed overlaying a digital map. The geographic view may also display network information such as, for example, node connections data, communication success rates for the nodes, and occurrences of communications events at the nodes. The nodes may be displayed in a manner representative of corresponding network information using, for example, a variety colors and icons.

FIELD OF THE INVENTION

The present invention relates to wireless networks for collecting data,and more particularly, to systems and methods of geographicallyvisualizing fixed wireless network layouts and performancecharacteristics for such networks.

BACKGROUND OF THE INVENTION

The collection of meter data from electrical energy, water, and gasmeters has traditionally been performed by human meter-readers. Themeter-reader travels to the meter location, which is frequently on thecustomer's premises, visually inspects the meter, and records thereading. The meter-reader may be prevented from gaining access to themeter as a result of inclement weather or, where the meter is locatedwithin the customer's premises, due to an absentee customer. Thismethodology of meter data collection is labor intensive, prone to humanerror, and often results in stale and inflexible metering data.

Some meters have been enhanced to include a one-way radio transmitterfor transmitting metering data to a receiving device. A personcollecting meter data that is equipped with an appropriate radioreceiver need only come into proximity with a meter to read the meterdata and need not visually inspect the meter. Thus, a meter-reader maywalk or drive by a meter location to take a meter reading. While thisrepresents an improvement over visiting and visually inspecting eachmeter, it still requires human involvement in the process.

An automated means for collecting meter data involves a fixed wirelessnetwork. Devices such as, for example, repeaters and gateways arepermanently affixed on rooftops and pole-tops and strategicallypositioned to receive data from enhanced meters fitted withradio-transmitters. Typically, these transmitters operate in the 902-928MHz range and employ Frequency Hopping Spread Spectrum (FHSS) technologyto spread the transmitted energy over a large portion of the availablebandwidth.

Data is transmitted from the meters to the repeaters and gateways andultimately communicated to a central location. While fixed wirelessnetworks greatly reduce human involvement in the process of meterreading, such systems require the installation and maintenance of afixed network of repeaters, gateways, and servers. Identifying anacceptable location for a repeater or server and physically placing thedevice in the desired location on top of a building or utility pole is atedious and labor-intensive operation. Furthermore, each meter that isinstalled in the network needs to be manually configured to communicatewith a particular portion of the established network. When a portion ofthe network fails to operate as intended, human intervention istypically required to test the effected components and reconfigure thenetwork to return it to operation.

Thus, while existing fixed wireless systems have reduced the need forhuman involvement in the daily collection of meter data, such systemsrequire substantial human investment in planning, installation, andmaintenance and are relatively inflexible and difficult to manage.Therefore, there is a need for systems and methods for providing ageographic visualization of the wireless network layout and networkinformation to simplify the maintenance and future planning of thenetwork.

SUMMARY OF THE INVENTION

The present invention is directed to systems and methods of providing ageographic view of nodes in a wireless network as well as networkinformation. In accordance with an aspect of the invention, a geographicview rendering tool receives geographic locations data for the nodes andrenders a geographic view displaying the nodes at their correspondinggeographic locations. The geographic locations data may include, forexample, a set of longitude and latitude coordinates or a center pointof a digital land parcel.

In accordance with another aspect of the invention, the geographic viewmay be displayed overlaying a digital map such that the geographic viewdisplays an accurate position of each node on the digital map. Thedigital map may be, for example, an aerial photograph, a topographicmap, an elevation map, a street map, or a land parcel.

In accordance with another aspect of the invention, the geographic viewrendering tool receives network information and renders the geographicview displaying the network information. The network information mayinclude, for example, node connections data, communication success ratesfor the nodes, and occurrences of communications events at the nodes.The network information may be shown by displaying the nodes and/ortheir connections in a variety colors and icons. A query may besubmitted requesting that network information be displayed based on aspecified criteria, and the geographic view may be rendered accordingly.

In accordance with another aspect of the invention, the view may bemanipulated to display one or more sub-networks. Each such sub-networkmay include, for example, a group of nodes that are all associated witha particular network component such as, for example, a collector,transformer, feeder or substation. The sub-networks may bedistinguished, for example, by color coding the connections between thenodes with each sub-network.

Additional features and advantages of the invention will be madeapparent from the following detailed description of illustrativeembodiments that proceeds with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description ofpreferred embodiments, is better understood when read in conjunctionwith the appended drawings. For the purpose of illustrating theinvention, there is shown in the drawings exemplary constructions of theinvention; however, the invention is not limited to the specific methodsand instrumentalities disclosed. In the drawings:

FIG. 1 is a diagram of a wireless system for collecting data from remotedevices;

FIG. 2 expands upon the diagram of FIG. 1 and illustrates a system inwhich the present invention is embodied;

FIG. 3 shows an exemplary process of producing a geographic view of anetwork layout;

FIG. 4 illustrates an exemplary geographic view;

FIG. 5 illustrates an exemplary geographic view selected for aparticular sub-network; and

FIG. 6 illustrates an exemplary geographic view overlaying a aerialphotograph.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Exemplary systems and methods for gathering meter data are describedbelow with reference to FIGS. 1-5. It will be appreciated by those ofordinary skill in the art that the description given herein with respectto those figures is for exemplary purposes only and is not intended inany way to limit the scope of potential embodiments.

Generally, a plurality of meter devices, which operate to track usage ofa service or commodity such as, for example, electricity, water, andgas, are operable to wirelessly communicate with each other. A collectoris operable to automatically identify and register meters forcommunication with the collector. When a meter is installed, the meterbecomes registered with the collector that can provide a communicationpath to the meter. The collectors receive and compile metering data froma plurality of meter devices via wireless communications. Acommunications server communicates with the collectors to retrieve thecompiled meter data.

FIG. 1 provides a diagram of an exemplary metering system 110. System110 comprises a plurality of meters 114, which are operable to sense andrecord usage of a service or commodity such as, for example,electricity, water, or gas. Meters 114 may be located at customerpremises such as, for example, a home or place of business. Meters 114comprise an antenna and are operable to transmit data, including serviceusage data, wirelessly. Meters 114 may be further operable to receivedata wirelessly as well. In an illustrative embodiment, meters 114 maybe, for example, a electrical meters manufactured by Elster Electricity,LLC.

System 110 further comprises collectors 116. Collectors 116 are alsometers operable to detect and record usage of a service or commoditysuch as, for example, electricity, water, or gas. Collectors 116comprise an antenna and are operable to send and receive datawirelessly. In particular, collectors 116 are operable to send data toand receive data from meters 114. In an illustrative embodiment, meters114 may be, for example, an electrical meter manufactured by ElsterElectricity, LLC.

A collector 116 and the meters 114 that are registered to the collector116 define a subnet/LAN 120 of system 110. As used herein, meters 114and collectors 116 maybe considered as nodes in the subnet 120. For eachsubnet/LAN 120, data is collected at collector 116 and periodicallytransmitted to a data collection server 206. The data collection server206 stores the data for analysis and preparation of bills. The datacollection server 206 may be a specially programmed general purposecomputing system and may communicate with collectors 116 wirelessly orvia a wire line connection such as, for example, a dial-up telephoneconnection or fixed wire network.

Generally, collector 116 and meters 114 communicate with and amongst oneanother using any one of several robust wireless techniques such as, forexample, frequency hopping spread spectrum (FHSS) and direct sequencespread spectrum (DSSS). As illustrated, meters 114 a are “first level”meters that communicate with collector 116, whereas meters 114 b arehigher level meters that communicate with other meters in the networkthat forward information to the collector 116.

Referring now to FIG. 2, there is illustrated a system 200 in which thepresent invention may be embodied. The system 200 includes a networkconfiguration system 202, a network management system (NMS) 204 and adata collection server 206 that together manage one or more subnets/LANs120 and their constituent nodes. The NMS 204 tracks changes in networkstate, such as new nodes registering/unregistering with the system 200,node communication paths changing, etc. This information is collectedfor each subnet/LAN 120 and are detected and forwarded to the networkconfiguration system 202 and data collection server 206.

In accordance with an aspect of the invention, communication betweennodes and the system 200 is accomplished using the LAN ID, however it ispreferable for customers to query and communicate with nodes using theirown identifier. To this end, a marriage file 208 may be used tocorrelate a customer serial number and LAN ID for each node (e.g.,meters 114 a) in the subnet/LAN 120. A device configuration database 210stores configuration information regarding the nodes. For example, inthe metering system 110, the device configuration database may the timeof use (TOU) program assignment for the meters 114 a communicating tothe system 200. A data collection requirements database 212 containsinformation regarding the data to be collected on a per node basis. Forexample, a user may specify that metering data such as load profile,demand, TOU, etc. is to be collected from particular meter(s) 114 a.Reports 214 containing information on the network configuration may beautomatically generated or in accordance with a user request.

The network management system (NMS) 204 maintains a database describingthe current state of the global fixed network system (current networkstate 220) and a database describing the historical state of the system(historical network state 222). The current network state 220 containsdata regarding current meter to collector assignments and other networkinformation for each subnet/LAN 120. The historical network state 222 isa database from which the state of the network at a particular point inthe past can be reconstructed. The NMS 204 is responsible for, amongstother things, providing reports 214 about the state of the network. TheNMS 204 may be accessed via an API 220 that is exposed to a userinterface 216 and a Customer Information System (CIS) 218. Otherexternal interfaces may be implemented in accordance with the presentinvention. In addition, the data collection requirements stored in thedatabase 212 may be set via the user interface 216 or CIS 218.

The data collection server 206 collects data from the nodes (e.g.,collectors 116) and stores the data in a database 224. The data includesmetering information, such as energy consumption and may be used forbilling purposes, etc. by a utility provider.

The network configuration system 202, network management system 204 anddata collection server 206 communicate with the nodes in each subnet/LAN120 via a communication system 226. The communication system 226 may bea Frequency Hopping Spread Spectrum radio network, a mesh network, aWi-Fi (802.11) network, a Wi-Max (802.16) network, a land line (POTS)network, etc., or any combination of the above and enables the system200 to communicate with the metering system 110.

FIG. 3 shows an exemplary process of producing a geographic view of anetwork layout. Client 146 may submit a geographic view request 320 viauser interface 216. The request 320 may be transferred over network 144,which may be a local area network (LAN) or a wide area network (WAN)such as the Internet. To enable request 320 to be placed over theInternet, the user interface 216 may be a browser-based interface thatmay be accessed via a web browser at client 146.

The request 320 is received by network management system 204, which,upon receiving the request, retrieves network information 322 fromcurrent and/or historical network state databases 220 and 222. Upon itscompilation, the network information 322 is forwarded to graph renderingtool 310. The network information 322 may include, for example, nodeconnections data, communication success rates for the nodes, andoccurrences of communications events at the nodes. A communicationsevent may be, for example, a node tampering incident, a node healthrelated alarm, a low battery indication, a maintenance indication, adisconnection, a reconnection, a power outage, a power restoration, or acommunications problem.

In addition to the network information 322, geographic location data 324is also provided to the rendering tool 310 via network configurationsystem 202. The geographic location data 324 may include longitude andlatitude coordinates for the nodes. Otherwise, if digital land parcelsare available for the area, the geographic location data 324 may includedigital data 324 a such as the center point of a digital land parcel atwhich a node is located. The geographic location data 324 may beprovided by a user via client 146 or by a third party such as, forexample, a geo-coding service or tool. Upon receiving the geographiclocation data 324, the rendering tool 310 associates each node with acorresponding geographic location.

Generally, rendering tool 310 uses network information 322, geographiclocation data 324, and digital data 326 to render geographic view 328,which displays each node in the network layout at its correspondinggeographic location. In addition to displaying the nodes, geographicview 328 may also display the network information 322. For example,geographic view 328 may display connections between the nodes, includingpaths between various network elements. Specifically, geographic view328 may display a path from each meter to its registered collector.Additionally, geographic view 328 may distinguish “orphaned” nodes whichare not connected to any other node in the network. Such orphaned nodesmay be displayed with a uniquely shaped icon. For example, connectednodes may be displayed with a circular icon, while orphaned nodes may bedisplayed with a triangular icon.

Geographic view 328 may also display a number of sub-networks within thenetwork layout. Each sub-network may include a group of nodes that areall associated with a particular network component such as, for example,a collector, transformer, feeder or substation. The sub-networks may bedistinguished by color coding the connections between the nodes withineach sub-network. Geographic view 328 may also display communicationsuccess rates for the nodes. For example, the icon for each node may becolor coded according to its corresponding communications success rate.Geographic view 328 may also display visual alerts to indicate theoccurrence of a communications event. For example, when an event occursat a particular node within a specified time period, a plus (“+”) iconmay be displayed adjacent to the node.

In addition to current network information, geographic view 328 may berendered based on historical network information stored in database 222and also historical digital maps or other topographical information.Geographic view 328 may be displayed in accordance with geographicinformation systems (GIS) standards, thereby enabling the view tointegrate well with third party tools that support rich GISfunctionality. For example, such tools may be used to easily identifymeters within a specified distance from another meter. The integrationalso allows the manipulation of a large display area, zooming in and outas necessary to examine the details.

FIG. 4 illustrates an exemplary geographic view 400. View 400 includes adisplay selection bar 410, which enables various network elements andnetwork information to be displayed. For example, selecting thecollector check box within bar 410 causes collectors to be displayedwithin view 400. As shown, the collectors are displayed with a largecircle icon. Additionally, connected meters are displayed with doticons, while orphaned meters are displayed with plus shaped icons. Themeter level check box of selection bar 410 is selected, which causesview 400 the size of each of each meter's icon to correspond to itsassociated meter level. Specifically, meters with the lowestcorresponding meter level zero are displayed with the small dot, whilemeters with the highest corresponding meter level four are displayedwith the large dot. Alternatively, the communications success rate checkbox could be selected, which would cause the size of each meter's iconto correspond to its associated communications success rate.Additionally, the color of each meter, rather than the size, may changeaccording to various attributes.

View 400 includes three collectors, the “2664” collector, the “2665”collector, and the “2666” collector. Each collector has a correspondingsub-network, which includes all meters that are registered to thecollector. The connections between the meters within each sub-networkare color coded. For example, connections between the meters in the“2664” sub-network may be displayed in yellow, connections between themeters in the “2665” sub-network may be displayed in blue, andconnections between the meters in the “2666” sub-network may bedisplayed in red. View 400 may be manipulated to show more or lessdetailed views of the network layout. For example, FIG. 5 illustrates aclose up view of the 2666 collector sub-network. The close up view ofFIG. 5 may be selected, for example, by clicking on the 2666 collectorwith an attached mouse. Additionally, the view may be adjusted to focuson the path of an individual meter to the 2666 collector by, forexample, clicking on the individual meter with the mouse.

Geographic view 328 may be displayed overlaying a digital map such as,for example, an aerial photograph, a topographic map, an elevation map,a street map, or a land parcel. For example, FIG. 6 illustratesgeographic view 328 overlaying an aerial photograph. As shown, theaerial photograph shows man-made and geographical structures surroundingnetwork elements. Displaying geographic view 328 in a “map view”overlaying a digital map provides a number of advantages with respect tonetwork management. For example, if a meter is communicating poorly, themap view may be used to quickly and easily determine the cause of theproblem. Specifically, an aerial photograph such as shown in FIG. 6 maybe used to determine whether there is a man-made or geographicobstruction in the path of the meter. Additionally, by facilitating theassessment of relative and/or absolute distances among various networkelements, the map view may be used to determine whether the problem is afunction of distance. If the meter is located in close proximity to thecollector or to a repeater, then the problem is probably not related todistance, and the map view may then be used to determine whether atamper condition or a meter hardware problem is responsible. The mapview may also be used to identify a cluster of nodes that areexperiencing a similar problem, such as, for example, a power outage.

The map view is also useful to identify instances of meter theft orvandalism. In particular, the map view may be used to identify a meterthat is stolen and then installed at a different location. For example,if an outlying meter is originally connected to a collector throughseveral intermediate nodes, and is later directly connected or connectedthrough fewer intermediate nodes, then this can be easily determinedfrom the map view. Specifically, the map view may show an unexpectedlong line from the meter to the collector or to a new repeater node.Likewise, if a meter is moved further from a collector, then the mapview may change to show a connection through several new repeaters.Furthermore, if the meter is moved so far away that it registers with anew collector, then the map view may change to show a long connectionfrom the previous meter location to the new collector, thereby makingthe tamper self-evident.

Rendering tool 310 may be queried to generate a view 328 that includesnetwork information based in specified criteria, and the view 328 may berendered accordingly. For example, if a meter is stolen and theninstalled elsewhere, then the malfunction may be identified by queryingfor connections that are no longer than a specified distance.Additionally, the query may request meters that have communicationcharacteristics that are significantly different from those of othermeters located in close proximity.

Geographic view 328 may be used to facilitate the future planning andmanagement of the network layout. For example, geographic view 328 maybe used to easily and rapidly identify when several meters in closeproximity to one another are experiencing communications problems. Itmay be then determined that new collectors and/or repeaters are neededin close proximity to those meters. Also, if an existing deployment ofmeters is to be expanded, then geographic view 328 may be used toidentify locations at which new collectors and/or repeaters should belocated. Specifically, geographic view 328 may be used to determine,based on maximum number of hops and the distances involved, whether anexisting collector network would be capable of supporting the new metersat the new locations. Additionally, if new collectors and/or repeatersare needed, geographic view 328 may be used to determine their expectedranges.

While systems and methods have been described and illustrated withreference to specific embodiments, those skilled in the art willrecognize that modification and variations may be made without departingfrom the principles described above and set forth in the followingclaims. Accordingly, reference should be made to the following claims asdescribing the scope of disclosed embodiments.

1. A method for providing a geographic view of nodes in a wirelessnetwork, comprising: receiving geographic location data and operatingstatus data for the nodes in the wireless network comprising a collectorand a plurality of meters that communicate wirelessly with thecollector, each of the meters having a wireless communication path tothe collector that is either a direct path or an indirect path throughone or more intermediate meters that serve as repeaters, the wirelesscommunication paths between each meter and the collector defining alayout of the network, the geographic location data comprising a digitalland parcel for each node; associating each node with a correspondinggeographic location by computing a center point of the node's digitalland parcel and associating the node with the computed center point; andrendering a geographic view of the nodes overlaying an aerialphotograph, the geographic view displaying each of the nodes at theircorresponding geographic location on the aerial photograph, thegeographic view further displaying the operating status data directlywithin the geographic view without first requiring interaction with anitem in the geographic view.
 2. The method of claim 1, wherein receivingthe geographic location data comprises receiving longitude coordinatesand latitude coordinates.
 3. The method of claim 1, further comprising:receiving node connection data; and displaying in the geographic view atleast one connection between the nodes.
 4. The method of claim 3,wherein displaying in the geographic view the at least one connectionbetween the nodes comprises displaying in the geographic view aconnection path from a meter to a collector.
 5. The method of claim 1,further comprising: receiving node connection data; and displaying inthe geographic view an orphaned node that is not connected to any of theother nodes.
 6. The method of claim 1, wherein displaying the operatingstatus data directly within the geographic view comprises displayingcommunications success rates for the nodes directly within thegeographic view.
 7. The method of claim 6, comprising displaying each ofthe nodes in a color corresponding to its communications success rate.8. The method of claim 1, wherein displaying the operating status datadirectly within the geographic view comprises displaying in thegeographic view a visual alert adjacent to a location of acommunications event occurrence to indicate the occurrence.
 9. Themethod of claim 8, comprising displaying in the geographic view thevisual alert corresponding to at least one member of a group comprisinga node tampering incident, a node health related alarm, a low batteryindication, a maintenance indication, a disconnection, a reconnection, apower outage, a power restoration, and a communications problem.
 10. Themethod of claim 1, further comprising displaying in the geographic viewa plurality of sub-networks within the network layout, each sub-networkdisplayed in a corresponding color.
 11. The method of claim 10,comprising displaying a plurality of sub-networks each comprising nodesthat are associated with a particular network component.
 12. The methodof claim 1, further comprising: receiving historical networkinformation; and displaying in the geographic view the historicalnetwork information.
 13. The method of claim 1, comprising rendering thegeographic view according to geographic information systems standards.14. The method of claim 1, further comprising: receiving a query todisplay network information in accordance with a specified criteria; anddisplaying the network information in accordance with the specifiedcriteria.
 15. The method of claim 1, further comprising rendering ageographic view that displays a tampered node at a new location that isdifferent from a previous location at which the tampered node wasdisplayed in a previously rendered geographic view.
 16. A computerreadable medium having computer executable instructions for performingthe steps recited in claim
 1. 17. A system for providing a geographicview of a network layout, comprising: a wireless local area network witha plurality of nodes comprising a collector and a plurality of metersthat communicate wirelessly with the collector, each of the metershaving a wireless communication path to the collector that is either adirect path or an indirect path through one or more intermediate metersthat serve as repeaters, the wireless communication paths between eachmeter and the collector defining a layout of the network; a geographicview rendering tool that receives geographic location data and operatingstatus data for the nodes the geographic location data comprising adigital land parcel for each node, associates each node with acorresponding geographic location by computing a center point of thenode's digital land parcel and associating the node with the computedcenter point, and renders the geographic view overlaying an aerialphotograph displaying the nodes at their corresponding geographiclocations on the aerial photograph, the geographic view furtherdisplaying the operating status data directly within the geographic viewwithout first requiring interaction with an item in the geographic view.18. The system of claim 17, wherein the geographic location datacomprises longitude coordinates and latitude coordinates.
 19. The systemof claim 17, wherein the geographic view displays network informationcollected from the wireless local area network.
 20. The system of claim19, wherein the network information comprises node communications pathsbetween nodes.
 21. The system of claim 19, wherein the geographic viewdisplays a connection path from a meter to a collector.
 22. The systemof claim 19, wherein the operating status data comprises communicationsuccess rates for the nodes.
 23. The system of claim 22, wherein thegeographic view displays the nodes in colors corresponding to theirassociated communications success rates.
 24. The system of claim 19,wherein the operating status data comprises data indicating anoccurrence of a communications event.
 25. The system of claim 24,wherein the geographic view displays a visual alert adjacent to alocation of the communications event occurrence to indicate theoccurrence.
 26. The system of claim 24, wherein the communications eventis at least one member of a group comprising a node tampering incident,a node health related alarm, a maintenance indication, a disconnection,a reconnection, a power outage, a power restoration, and acommunications problem.
 27. The system of claim 19, wherein thegeographic view displays a plurality of sub-networks within the networklayout, each sub-network displayed in a corresponding color.
 28. Thesystem of claim 27, wherein each sub-network comprises nodes that areassociated with a particular network component.
 29. The system of claim19, wherein the network information is historical network information.30. The system of claim 17, wherein the geographic view is renderedaccording to geographic information systems standards.
 31. The system ofclaim 17, wherein the geographic view rendering tool can be queried todisplay the geographic view in accordance with a specified criteria. 32.The system of claim 17, wherein the geographic view displays a tamperednode at a new location that is different from a previous location atwhich the tampered node was displayed in a previously renderedgeographic view.
 33. The system of claim 20, wherein the nodecommunications paths changes dynamically, and the geographic viewdisplays dynamic changes to the node communications paths.
 34. Thesystem of claim 33, further comprising a network management system thatpolls network elements to track the dynamic changes to the nodecommunications paths.
 35. The system of claim 33, further comprising anetwork management system that is notified by network elements of thedynamic changes to the node communications paths.
 36. The system ofclaim 17, wherein the operating status data changes dynamically, and thegeographic view displays dynamic changes to the operating status data.37. The system of claim 36, further comprising a network managementsystem that polls network elements to track the dynamic changes to theoperating status data.
 38. The system of claim 36, further comprising anetwork management system that is notified by network elements of thedynamic changes to the operating status data.
 39. The method of claim 3,further comprising: receiving updated node connection data comprisingdata regarding dynamic changes to node communications paths; anddisplaying in the geographic view the dynamic changes to the nodecommunications paths.
 40. The method of claim 39, further comprising:polling, by a network management system, network elements to track thedynamic changes to the node communications paths.
 41. The method ofclaim 39, further comprising: receiving at a network management systemfrom a network element a notification of the dynamic changes to the nodecommunications paths.
 42. The method of claim 1, further comprising:receiving updated operating status data comprising dynamic changes tothe operating status data; and displaying in the geographic view thedynamic changes to the operating status data.
 43. The method of claim42, further comprising: polling, by a network management system, networkelements to track the dynamic changes to the operating status data. 44.The method of claim 42, further comprising: receiving at a networkmanagement system from a network element a notification of the dynamicchanges to the operating status data.